startbuffer
Command/ startcolumnset
Command/ startcomment
Command/ startdelimitedtext
Command/ startdescription
Command/ starteffect
Command/ startenumeration
Command/ startfittingpage
Command/ startfloattext
Command/ startformula
Command/ startframedtext
Command/ starthelp
Command/ start
},
inbetween={\directsetup[small:whitespace]}]
\starttext
\input knuth
\startdescription{Knuth}
\input knuth
\stopdescription
\stoptext
How can I get a different whitespace inside the description?
\setupdescription
[description]
[style={\setupwhitespace[small
]}]
\starttext
\input knuth
\startdescription{Knuth}
\input knuth
\stopdescription
\stoptext
How can I get a different whitespace inside the description?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
other commands of this kind?
\usemodule[setups]
\starttext
When you describe a command, e.g.
\type{\startdescription{\cmdbasicsetup[...]} ... \stopdescription}:
\startbuffer [basicsetup]
\cmdbasicsetup [startxtable]
\stopbuffer
\typebuffer [basicsetup]
\ge
to be used
> > according to needs?
> >
> > Are there other commands of this kind?
>
> \usemodule[setups]
>
> \starttext
>
> When you describe a command, e.g.
> \type{\startdescription{\cmdbasicsetup[...]} ... \stopdescription}:
>
> \startbuffer [basi
{\startdescription{\cmdbasicsetup[...]} ... \stopdescription}:
\startbuffer [basicsetup]
\cmdbasicsetup [startxtable]
\stopbuffer
\typebuffer [basicsetup]
\getbuffer [basicsetup]
When you show the syntax of a command without the options:
\startbuffer [shortsetup]
\cmdshortsetup [startxtable]
\stopbuffer
stick to one line.
I guess it would be better to use a paragraphs or column environment for long
labels but the ConTeXt is generated by pandoc, which writes 'definition lists'
as \startdescription \stopdescription.___
[before=\nowhitespace, after=\nowhitespace]
>>
>> \starttext
>>
>> \startdescription{Short term:}
>> Items with short terms are fine.
>> \stopdescription
>>
>> \startdescription{This is a really long term:}
>> Long term + short definition
>>
below.
Here's an example:
\setuppapersize[A5]
\setupalign[flushleft, nothyphenated]
\definedescription[description]
[before=\nowhitespace, after=\nowhitespace]
\starttext
\startdescription{Short term:}
Items with short terms are fine.
\stopdescription
\startdescription{This is a really
{} cap
17 \letterbar{} \letterbar{}
18
19 \startdescription{Term 1}
20 Definition 1
21 \stopdescription
22
23 \startdescription{Term 2}
24 Definition 2a
25
26 Definition 2b
27 \stopdescription
28
29 \section[gràfica-duna-funció]{Gràfica d'una
into the margin
\definedescription
[description]
[alternative=hanging,
width=broad]
\starttext
\startdescription{conclusion that}
\input knuth
\stopdescription
\startdescription{conclusion that the designer of a new system must not only be
literally}
\input knuth
\stopdescription
\stoptext
On 3/27/2013 7:55 PM, Marco Patzer wrote:
%% Wide descriptions protruding into the margin
\definedescription
[description]
[alternative=hanging,
width=broad]
\starttext
\startdescription{conclusion that}
\input knuth
\stopdescription
\startdescription{conclusion
Hi,
with wide description heads I have the problem that the following
description protrudes into the margin.
\definedescription
[description]
[alternative=hanging,
width=broad]
\starttext
\startdescription{conclusion that}
\input knuth
\stopdescription
\startdescription{conclusion
=\zeropoint
.75\emwidth\else\constructionsheaddistance\fi
\hskip\ifdim\constructionsheaddistance=\zeropoint
.75\emwidth\else\constructionsheaddistance\fi
\useconstructionstyleandcolor\c!style\c!color
\ignorespaces
\stopsetups
\protect
\starttext
\startdescription{conclusion that}
\input knuth
{\bf \pagenumber}\quad \cap {maps\ \MapsNumber}}]
[\AuHead]
\setupfootertexts
}
\def\fulltextwidth{457pt}
\def\startdescription
{\blank
\bgroup
\def\sym##1{\par\noindent\hbox{\bf\kern -16pt ##1}\hskip 12pt}
\startnarrower[left]
}
\def\stopdescription
{\par \stopnarrower
\useconstructionstyleandcolor\c!style\c!color
\ignorespaces
\stopsetups
\protect
\definedescription[description][alternative=right,headalign=]
\starttext
BEFORE
\startdescription{Knuth}
\input knuth
\stopdescription
AFTER
\stoptext
Wolfgang
[description]
[alternative=top,
headstyle=bold,
headcolor=blue,
headcommand={\offset[x=-1cm]},
margin=1cm]
\starttext
\input tufte
\startdescription{Tufte}
\input tufte
\stopdescription
\stoptext
Wolfgang
___
If your
={\bf\addff{smcp}}]
\setupbodyfont[pagella]
\starttext
\input ward
\startdescription{Ward}
\input ward
\stopdescription
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add an entry
cleaner solution. (Again, I already saw message
about change from `location=' to `alternative='.)
\starttext
\input tufte
\startdescription{Tufte}
\input tufte
\stopdescription
\stoptext
Wolfgang
---
WBR, Vladimir Lomov
--
Banacek's Eighteenth Polish Proverb:
The hippo has
braces are used for arguments which are printed (e.g. \startdescription{…}).
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http
(i.e. \setnumber[footnote][123]), this
was changed because
braces are used for arguments which are printed (e.g. \startdescription{…}).
yes, great decision to change this. this way context gets more and more
stringent.
thank you! st
just want a \definition to typeset? Shouldn't the command already be
available?
When there would be a predefined description command I would prefer \description
and \startdescription but not \definition but it’s hard to say which command
should
be available by default everyone has a different
On Thu, 2012-01-19 at 00:12 +0100, Wolfgang Schuster wrote:
When there would be a predefined description command I would prefer
\description
and \startdescription but not \definition but it’s hard to say which command
should
be available by default everyone has a different opinion.
Thanks
\Umathquad\displaystyle is not set ...
52 \startparagraph \input zapf (Zapf) \stopparagraph
53
54 \startdescription {Ward} \input ward \stopdescription
55
56 \startdescription {Tufte} \input tufte \stopdescription
57
58 \startparagraph \input knuth (Knuth) \stopparagraph
Hi,
is \startdescription a valid command? I've found it in the reference section on
the wiki (generated cont-en.xml) Or is it meant as a pattern/template for
another command?
Patrick
___
If your question
Am 05.10.2010 um 14:50 schrieb Patrick Gundlach:
Hi,
is \startdescription a valid command? I've found it in the reference section
on the wiki (generated cont-en.xml) Or is it meant as a pattern/template for
another command?
The reference section on the wiki has a problem with generated
Am 05.10.2010 um 15:13 schrieb Wolfgang Schuster:
[...]
thanks, I've updated the wiki.
Patrick
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
\noshowargumenterror -\let
\expectedarguments \noexpectedarguments
\dodoubleempty #1-\noshowargumenterror
\doifnextcharelse
[{\dodoubletestemp...
\startENUM -\dodoubleempty \@@startdescription
!broad,%
\c!headstyle=\@@exmintrostyle,\c!style=\@@exmstyle,%
\c!before=,\c!inbetween=,\c!after=,%
\c!text=\placeannotationstart]
etcetera
The error message in latest context beta is:
! Use of \@@startdescription doesn't match its definition.
\doifnextoptionalelse
this experiment.
Something with processcomma?
By the way, could it be related to some other error I get in mkiv in
processing a description? There in the log similarly something with
parameterlists seems at hand:
! Use of \@@startdescription doesn't match its definition.
\doifnextoptionalelse
it be related to some other error I get in mkiv in
processing a description? There in the log similarly something with
parameterlists seems at hand:
! Use of \@@startdescription doesn't match its definition.
\doifnextoptionalelse ...\nextoptionalcommandyes
actual problem is with a \startframed directly after a description header
...
which is for me
\startdescription{...}
\startframed
...
\stopframed
...
and what you showed is something different and putting \page[no] between
\startdescription and \startframed is not what I would suggest
, % use command parameter
command=\gobbleoneargument] % remove description text
\starttext
\startdescription{Knuth}
\input knuth
\stopdescription
\startdescription{Zapf}
\input zapf
\stopdescription
\stoptext
Wolfgang
\startbuffer[name] \stopbuffer
\startcolor[name] \stopcolor
\startcolumns[settings] \stopcolumns
\startcombination[matrix] \stopcombination
\startcomment[name][settings] \stopcomment
\startcomponent file \stopcomponent
\startdescription{text} \stopdescription
\startdocument[name] \stopdocument
To be added to syst-ext.tex
\def\dowithoptargument#1%
{\def\useoneargument##1{#1{##1}}
\def\fakeoneargument{#1{}}
\doifnextcharelse\bgroup{\useoneargument}{\fakeoneargument}}
%D Patch for core-des.tex
\def\@@startdescription[#1][#2]%
{\def\currentdescription{#1}%
\doifelse
having two different theorems
(titledtheorem and nontitledtheorem) or always adding {} at the
beginning of each theorem. I want the behaviour closer to title=maybe.
I do not understand why \@@startdescription contains
\dowithwargument{\@@startsomedescription{#1}[#2]}
I would prefer it to contain
=]
\startoperation
AuctionClient::providePersData($p$: Person)
\stopoperation
\startdescription
Fournit les données personnelles
nécessaires à la création d'un compte, encapsulées dans un
objet $p$.
\stopdescription
\startpost
\startcode
if (self.checkPersData(p
]}%
\setvalue{\e!start#1}{\dodoubleempty\@@startdescription[#1]}%
\setvalue{\e!stop #1}{\@@stopdescription{#1}}}%
And when using commands with brackets in argumets like:
\definedescription[desc][before=\blank[small]]
ConTeXt will give many errors, so arguments needs to be grouped (before
. Another part of a learning
curve
which if you want adoption you should try to avoid. But maybe it is
impossible to make ConTeXt more 'forgiving'.
The alternative is \startdescription\stopdescription which is
logically
nicer, but adds inconvenience to the typing/editing
IMO LaTeX here does a better
you should try to avoid. But maybe it is
impossible to make ConTeXt more 'forgiving'.
The alternative is \startdescription\stopdescription which is logically
nicer, but adds inconvenience to the typing/editing
IMO LaTeX here does a better user-interface job (not just because I happen
to know LaTeX
40 matches
Mail list logo
